Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
V-91113 | JUNI-ND-000240 | SV-101213r1_rule | Medium |
Description |
---|
Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent the auditing of critical events. Misconfigured audits may degrade the system's performance by overwhelming the audit log. Misconfigured audits may also make it more difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. |
STIG | Date |
---|---|
Juniper Router NDM Security Technical Implementation Guide | 2018-11-14 |
Check Text ( C-90267r2_chk ) |
---|
Review the router configuration to verify that it is compliant with this requirement. The configuration example below allows only users belonging to the AUDITOR class to configure the logging parameters. system { login { class AUDITOR { permissions [configure view-configuration]; allow-configuration "(system syslog)"; } class SR_ENGINEER { permissions all; deny-configuration "(system syslog)"; } } } If the router is not configured to allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited, this is a finding. |
Fix Text (F-97311r2_fix) |
---|
Create a login class that provides the permission to configure logging parameters as well as a classes that do not allow configuration of logging parameters as shown in the example below. set login class AUDITOR permissions [configure view-configuration] set login class AUDITOR allow-configuration "(system syslog)" Note: The auditor must also be allowed to view the configuration to verify. set login class SR_ENGINEER permissions all set login class SR_ENGINEER deny-configuration "(system syslog)" Note: A user assigned to the Superuser class would have the ability to change logging parameters. It is NOT recommended to assign this class to any router administrator. |